Thanks for your support, Bart. ❤️

Documentation you've added shows to escape it with \, but your example escapes with \\?

Documentation you've added shows to escape it with \, but your example escapes with \\?

It'll be because it's inside JSON I imagine.

As for the whole escape using backslash - I have reservations (but cannot put my finger on why). Things like CSV usually just double up the character :: or html use an alt code.

Ideally, We would support better structured property for specifying the page (not just a string joined by a random colon) but I understand this is a throwback from dashboard 1. In fact, I've always been super curious why we don't support the node ID. There is no ambiguity and if I ever change the title of the page, my UI control still works.

Hi guys,
Quick response because familly stuff going on.

1. Yes like Steve says, escape is single \ but you need extra \ to get a valid json. I will need to correct the docs later on.
2. Indeed while creating a fix, I indeed had a bad feeling. Not about the fix, but about the long string path. A separate page and group property is nicer imho.
3. Yes the node id makes sense. Perhaps as an alternative way of working?

Yes the node id makes sense. Perhaps as an alternative way of working?

Yeah, I think this is the better solution, but we do need to support the existing methodology for backward compatibility. Maybe we getNode given the string first, if no node is returned, then assume it's page/group name combo?

Getting a Node's ID in Node-RED is also quite unintuitive though (especially for config nodes), so would need to improve the docs on this.

@joepavitt
I will try to have a look at this during the weekend.